docs: Add support for F5 WAF for NGINX to NIC release page #1439
+41
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
travisamartin
approved these changes
Nov 13, 2025
✅ Deploy Preview will be available once build job completes!
|
JTorreG
force-pushed
the
nic/add-matrix
branch
from
69855f6 to
9fdd187
Compare
travisamartin
approved these changes
Nov 17, 2025
Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>
pdabelf5
approved these changes
Nov 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Added compatibility matrix and support details for F5 WAF in NGINX to NIC release page.
Added WAF comp. matrix to technical specifications.
closes #1115
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩